2016-07-14 - 26998 - Spec - CH Robinson New Output type ZCHR #chr
SPECIFICATIONS
26998 - Spec - CH Robinson New Output type ZCHR.
Purpose
CH Robinson New Output type.
Admin Info
| Purpose |
CH Robinson New Output type. |
| Requested By |
Jingsha |
| Spec Created By |
Adithya |
| Spec Created Date |
07/17/2016 |
| Spec QA by |
Adithya |
| Objects |
SPRO ZXM06U33 ZSNCOR05 TFRMT TFRM EDISEGMENT Z1EXTBT RV61B907 RV61B908TFRM |
| Document Status |
Complete |
Estimates
| Sl.No |
Activity |
Estimation in Hours |
| 1 |
Research |
08 |
| 2 |
Documentation |
08 |
| 3 |
Development/ Config |
40 |
| 4 |
Unit test in DEV |
32 |
| 5 |
Unit test in QUA |
|
| 6 |
Other activity |
|
| TOTAL |
88 |
References
Prior Tickets
[Provide links of prior associated Spec / Break Fix BOSS document(s)]Documents
[Attach any document(s) received for the requirement(s)]
Spec Changes
[List the changes made to program after the approval of the original requirement along with the Date on which the change request was received and the name of the initiator]
| Sl. |
Change Details |
Requested By |
Requested On |
Notes if any |
| 1 |
IDOC generation for Change POs ZCHR for new POs & ZSNC for old POs. Change IDOC shall not be generated when Inbound Delivery is created. |
Jingsha |
07/21/2016 |
|
| 2 |
Add two new fields in the IDOC. User Created by and Company Code address |
Jingsha |
0729/2016 |
|
| 3 |
Change the Country code field to ISO standards. |
Jingsha |
08/04/2016 |
|
| 4 |
Add vendor address in ORDCHG IDOC so that it shown up as ORDERS IDOC |
Jingsha |
08/08/2016 |
|
| 5 |
Add EAN/UPC number in the E1J3AIM segment of ORDCHG IDOC as it is shown up in ORDERS IDOC |
Jingsha |
08/08/2016 |
Functional Requirement
Purpose/WHY:
[Explain the purpose of the project and the reason why this requirement has come]As CH Robinson PO management is eventually going to be replace the existing SNC system for the PO process, PO data no more shall be going to SNC via PIP, and it has to be stored as a file in a application server so that it will be sent to CHR from there.
There shall be a New PO output "ZCHR" which shall be generated when a PO is created/changed/Deleted.
Data in the IDOC which is generated with the new output shall be same as the data of the ZSNC output IDOC.
Currently CH Robinson is being implemented for NA and Canada Plants for i.e. for company codes 0010 & 0020.
In Scope:
[List the activities to be included in scope]Out of Scope:
[Out of scope activities]Solution Summary
[Discuss this section with Requester and get approval prior to beginning work]
Create a new message out put type "ZCHR" similar to "ZSNC" with the same Basic type, Message type & Extension.
As the new message out put type shall be triggered only for NA and Canada Plants, A new Access Sequence is to be created for Vendor and Company Code Combination.
Note: Going Forward we may have to use the same access sequence which is used for ZCHR shall be used for the SNC out put type as well i.e. for "ZSNC" because currently ZSNC message output type is maintained for the PO Doc Type, Pur Org & Vendor, there may be a chance of ZSNC message getting generated for the NA & Canada plant POs
Creation of new access sequence: "0007"
This access sequence is being used in new message out put type "ZCHR"
Creation of new Message out put type: "ZCHR"
Setting for placing the text file in the application server.
A Port has to be created in WE21. Name of the Port:
Maintain partner profiles for the port which is created in WE20.
Add ORDERS and ORDCHG Creation/Change message types in the Partner profiles Out Bound parameters.
Add Extension "ZSNCOR05" in outbound options tab.
Add New Message output type in Message Control tab, Process code shall be ME10 for Create O/P and ME11 for change.
Note : To get the custom fields in the new Outputs IDOC we have to change the exit "ZXM06U33" so as the custom fields and elements are shown up in the IDOC.
Test Plan
[List test scenarios/cases to be executed here]Check if new Output type is triggered automatically and processed immediately for company code 10 & 20 & CHR Vendors only
| Test ID |
Test Scenario |
Expected Results |
| CHR01 |
Create a PO and validate the Following: 1. New output type shall be triggered. 2. Out put type shall be processed immediately 3. IDOC and File placing. |
1.The new output type shall be triggered when a PO is created for company codes 10 & 20 and with the CHR Vendor. 2. The Output shall be processed immediately 3. An IDOC shall be generated and a file shall be placed in the AL11 Folder maintained in the port. |
| CHR02 |
Change the PO and validate the Following: 1. New output type shall be triggered. 2. Out put type shall be processed immediately 3. IDOC and File placing. |
All the Data of the PO shall be sent again. 1.The new output type shall be triggered when a PO is created for company codes 10 & 20 and with the CHR Vendor. 2. The Output shall be processed immediately 3. An IDOC shall be generated and a file shall be placed in the AL11 Folder maintained in the port. |
| CHR03 |
Validate if data in SNC IDOC and ZCHR IDOC is same (Just for validation of data not a test scenario) |
Data in both the idocs shall be same with the custom fields in it. Same as the SNC IDOC. |
| CHR04 |
Create a PO with SNC Vendor and company code 0010 Validate that no ZSNC Output message shall be generated |
No ZSNC Message shall be generated. |
| CHR05 |
Change the CHR PO after the Inbound Delivery is created. |
No ZCHR Message shall be generated for the change in the PO after Inbound Delivery is created |
| CHR06 |
Create the CHR and SNC PO. Validate the data in the SNC IDOC Validate the data in the CHR IDOC |
1. SNC IDOC shall not have the new segment which is created for the Bill to and User created by fields 2. CHR shall have the new segment which is created for the Bill to and User created by fields. |
| CHR07 |
Create/Change the CHR PO |
Data in new segment shall be there. |
Email on 07/21/2016:
IDOC communication from SAP ECC to CHR. Below are the requirements, and as I mention, all requirements needs to be fulfilled before going live
1. No confirmation key update is required, and all info records going forward will still have ZNEC or ZSNC.
2. Both ZCHR and ZSNC output condition access sequences need to be updated to include company code and vendor ID as selection criteria.
Maintain the new access sequence for both the output types
3. Changes such as Delivery Date, Ex factory date, Price, Quantity, adding a line, deleting a line etc. should trigger ZCHR IDOC output.
Same as when the SNC IDOC triggers for change POS
4. Only new POs need to be sent to CHR. Existing POs should not be sent to CHR.
I understand we have discussed using Creation date or last created PO as the selection criterial. I have talked to Jeff regarding this, his opinion however, is below:
(i). For brand new POs, use the condition records (vendor # and Company code) to determine whether it should be ZCHR or ZSNC
(ii). For PO changes, check to see whether there is existing ZCHR output type, if there is yes, then trigger IDOC, if not, do not trigger (Note that this is different from what we talked about). Please let me know
whether this is technically possible, and how much effort would be needed if it is possible.?
Maintain condition records for ZSNC and ZCHR for Company Code and Vendor Combination for 0010 & 0020 as we are going live with two company codes.
Maintain a routine for ZCHR so as it checks earlier Outputs in PO if it is ZSNC is triggered then stop ZCHR output, If it is ZCHR output ZCHR shall be triggered.
Maintain a routine for ZSNC so as it checks earlier Outputs in PO if it is ZSNC then trigger ZSNC and if it is ZCHR then it shall stop and not trigger the Output ZSNC.
5. If a PO has IBD, no ZCHR output IDOC should be generated. This is to ensure that once the shipments are on water, even if the PO date is changed, we do not want the change to be sent to CHR.
Also Please confirm that if Inbound Delivery for the change output in PO shall be considered for which line in the PO ?
Email on 07/29/2016
For CHR IDOC add two more information.
1) Bill-to party, which is the PO company code’s address
2) Creator of the PO
Use the existing extension "ZSNCOR05" which is used in the SNC IDOC to get add the new segment with the two fields above.
The new segment added shall be triggered in only ZCHR Idoc.
In Q 600 on 08/08/2016
When the PO is changed, unlike SNC only Changed Items are only included in the IDOC. SNC idoc also sends unchanged Items of the PO, the entire PO would be send for any change in the PO.
The unchanged items would be with action type 004.
Add ZCHR message type in include "ZXM06U02" so that the unchanged items in the PO would be triggered with action type 004 in the Change ORDCHG IDOC which will send the whole Po similar to SNC.
Change the
Solution Details
[Provide complete technical details for configuration or programming here]
Create Access sequence - Transport.
Create Out put types - Has to be done in each server and client.
Create Port and Assign in Partner Profiles
Maintain Message types in partner profiles.
Change the User Exit so as to get the custom fields in the IDOC.
Change the access sequence in the ZSNC output type so as these messages shall not be triggered any more for the Company codes 10 & 20.
Note When ever we go live for new company codes those company codes has to be added in the routines for generatinf ZCHR output type
08/05/2016: Company Code logic in routines have been removed on date 08/05/2016
Sent in the 2nd Release.
Release sent on 08/08/2016- Release # 3
Vendor full address is to be sent in the IDOC similar to Create IDOC.
EAN/UPC numbers would be sent in the change IDOC similar to Create IDOC.
Non Updating POs line shall be sent in the change IDOC.
Issues
[List Issues / Bugs identified in configuration or development]